Closed
Conversation
No point in not supporting it, as no API used is exclusive to any versions higher Should wait for LapisCore to update first, but not required, as the plugin will still function with LapisCore being built on 1.20.2
Member
|
This has been fixed by setting the API version in the plugin yaml |
Contributor
Author
wdym breaking changes? if spigot were to remove anything from their api it'd most likely break thousands of plugins that support earlier versions, so its unlikely they do |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No point in not supporting it, as no API used is exclusive to any versions higher
Should wait for LapisCore to update first (LapisPlugins/LapisCore#11), but not required, as the plugin will still function with LapisCore being built on 1.20.2